home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000315_news@columbia.edu_Wed Nov 30 17:50:41 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA21103
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 1 Dec 1994 08:41:21 -0500
Received: by apakabar.cc.columbia.edu id AA04090
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 1 Dec 1994 08:41:18 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!caen!math.ohio-state.edu!cs.utexas.edu!convex!convex!constellation!news.uoknor.edu!news.ualr.edu!news.ach.uams.edu!news
From: bruce@mail.uams.edu (Bruce Hulsey)
Newsgroups: comp.protocols.kermit.misc
Subject: Help with SmarTerm 2xx and C-Kermit
Date: 30 Nov 1994 17:50:41 GMT
Organization: UAMS-Computing Services
Lines: 37
Message-Id: <3bie1h$1dp@alvin.ach.uams.edu>
Nntp-Posting-Host: 144.30.1.66
X-Newsreader: WinVN 0.91.6
Apparently-To: kermit.misc@watsun.cc.columbia.edu
Greetings!
We're currently running C-Kermit 5a(189) under OpenVMS 1.5. We have a
number of users who are using older versions of Persoft's comm programs
SmarTerm 220 and SmarTerm 240 on their pc's. Unfortunately, these
programs' implementations of kermit don't work properly when trying to
GET a file from C-Kermit when it is in server mode. Every other kermit
file transfer appears to work ok between SmarTerm and C-Kermit, i.e.,
interactive (non-server mode) send/receive operations work fine in both
directions. SEND transfers with C-Kermit in server mode seems to work ok
as well. Only GETs from C-Kermit fail.
I understand from a post that I received from Frank da Cruz regarding
this that many comm packages simply don't follow the kermit protocol the
way they should, but I'd still like to try to get it to work if possible.
I do have packet logs from attempted GET transfers using SmarTerm 240
(which doesn't work) and SmarTerm 340 (which does work), and SmarTerm 240
does send a strange packet up front which SmarTerm 340 does not (the
strange packet is <SOH>#N3<CR> ). Quite a few users are a little
concerned about this since everything worked fine before we moved from
Kermit-32 version 3.3.111 on a VAX to C-Kermit on an Alpha processor.
If anyone has found a workaround for this problem, please let me know.
At this point, I don't want to tell everyone they have to upgrade their
comm software or switch them over to something else, but I suppose that I
will if I have to...
Also, I can't find any mention of Kermit-32 in the listing of Kermit
software versions in the "Using C-Kermit" book. Is Kermit-32 a
'legitimate' member of the Kermit family?
All help is greatly appreciated...thanks!
Bruce Hulsey
Univ. of Arkansas for Medical Sciences
bruce@mail.uams.edu
bbhulsey@life.uams.edu